
Musashi Date
25TH miss
40
|
Posted - 2013.11.04 19:40:00 -
[1] - Quote
Machine Info and Settings
DirectX version your client was running (Cntrl+F to see this information):
Running on DX9; the launcher settings says "! Your computer only supports DirectX 9" and the selection box has been greyed with DirectX9 in it. This was.. peculiar because my dxdiag clearly says I have DirectX 11 on.
OS version:Win7 64bit CPU:Core2Duo [email protected] GPU:Radeon 4670 2Gb RAM:4Gb DDR2
How many clients were you running at the same time?Four clients
Graphic setting of the client (low / medium / high): - Anti-Aliasing:Disabled - Shader Quality: Low - Texture Quality: Low - LOD Quality:Low
User Experience
Total Memory before Poitot jump: about ~600Mb Total Memory after Poitot jump: ~1,100Mb
FPS went down to below 5fps during the fight, but CPU performance was around 45~55% and was really impressive. Some of my clients was just peaking near 50% utilization, and only the target caller (assigned sentries) peaked up to 95%~100% CPU.
Working set size is 818Mb on the target caller, and 764~706Mb on the others.
Average FPS during the fight at the gate in Poitot - zoomed out:~5 Average FPS during the fight at the gate in Poitot - zoomed in:~5 Was client performance better or worse compared to your TQ experience with the same settings and fleet size? (1=way worse, 5=same, 10=OMG this is awesome)3 Did you experience any disconnects or crashes? No client crashed for this masstest We added texture LODing to reduce the client memory, textures loading when zooming in and out can be delayed in heavy scenes. Did you feel this degraded the visual experience?
Oh so that was what I saw while zooming out on my ship, the muddied colors/textures definitely caught my attention at low settings. I just tested it again and it starts at 11 zoom buttons out, then at 22 and then it stays the same after that. So.. three levels? Maybe increase the second one to around 22 and the third to 30.
The effect is also present in the fitting window, and I can see only 2 levels which seems to start at 4 mousewheels out. And it looks like the feature is missing in both the ship hangar view and the captains quarters mode.
[i] Describe your experience, make comments, suggestions, etc.:
The usual module lag and overview lag is there, even as I was zoomed out and away from the fray.
There was this thing I stumbled upon though, with a Survey Scanner for asteroids. When pressing CTRL on the keyboard, I can lock objects from the overview, fleet broadcast history and the Survey scanner results. While pressing X on the keyboard, I can broadcast targets from the overview, the fleet broadcast history, but not on the survey scanner results? I tested this a couple of times, and it seems the X broadcast key is broken for the survey scanner results window. |